- Replace unnecessary Promise.allSettled with direct dispose calls in execute-build.ts
- Rename SourceFileCache dispose() to override clear() and call super.clear() to clear base Map alongside internal cache structures

…#33715)

Disposes the Angular compilation and bundler contexts within the build execution
for non-watch builds once bundling has completed. This terminates the TypeScript
compilation worker and JavaScript transformation workers before the post-bundle
steps (chunk optimization, i18n inlining, index generation) execute instead of
after all results have been emitted. Repeat compilation disposal calls now return
the in progress disposal to ensure all callers can await completion of the
underlying compiler shutdown. The result disposal also releases the incremental
build caches which can retain the emitted contents of every TypeScript file
within the program. This reduces the peak memory usage of the build for both
the non-watch early disposal and watch mode teardown.

Closes #33368

PR Close #33715

…33715)

When an unhandled exception is thrown during a build (such as IndexHtmlGenerator.readIndex throwing when an index HTML file is missing or unreadable), executeBuild() previously re-threw without calling .dispose() on executionResult or angularCompilationContext. Consequently, open ESBuild child processes, TypeScript compiler worker threads, and SQLite database connections prevented the Node.js process from exiting.

This commit addresses the issue by:
1. Wrapping the entire body of executeBuild() in a try...catch block and instantiating executionResult immediately after bundlerContexts is created, so any thrown error reliably disposes all worker pools and AST caches before re-throwing.
2. Closing the SQLite cache store (angular-i18n.db) in I18nInliner.close() alongside worker pool destruction.
3. Ensuring Sass workers are shut down in build-action even if an initial --watch build throws an exception.

Closes #33716

PR Close #33715

…33715)

When an unhandled exception is thrown during a build (such as IndexHtmlGenerator.readIndex throwing when an index HTML file is missing or unreadable), executeBuild() previously re-threw without calling .dispose() on executionResult or angularCompilationContext. Consequently, open ESBuild child processes, TypeScript compiler worker threads, and SQLite database connections prevented the Node.js process from exiting.

This commit addresses the issue by:
1. Wrapping the entire body of executeBuild() in a try...catch block and instantiating executionResult immediately after bundlerContexts is created, so any thrown error reliably disposes all worker pools and AST caches before re-throwing.
2. Closing the SQLite cache store (angular-i18n.db) in I18nInliner.close() alongside worker pool destruction.
3. Ensuring Sass workers are shut down in build-action even if an initial --watch build throws an exception.

Closes #33716

PR Close #33715